I'm trying to run some commands on our CAS servers, and I'm getting the error "load quota for the system has been exceeded".  I'm running two CAS servers in an Exchange 2013 Standard Environment, running on Windows 2012 Standard servers.  Both my CAS servers are getting the error.  I also have two MBX servers, and I can access EMS on those just fine.

I checked another thread that had a similar issue for Exchange 2010:  https://social.technet.microsoft.com/Forums/exchange/en-US/1cc17514-44dc-41d9-b319-3232107490c0/cant-open-emc-or-ems-for-exchange-2010-from-local-machine?forum=exchange2010

However none of the fixes they described worked, and some of the fixes look like they're out of date.

Here's the full error message.  It tries to connect to both CAS's, fails, and then connects to the first MBX it can.

VERBOSE: Connecting to cas2013.contoso.com.
New-PSSession : [cas2013.contoso.com] Connecting to remote server cas2013.contoso.com failed with the following error message :
The WS-Management service cannot process the request. The load quota for the system has been exceeded. Send future
requests at a slower rate or raise the system quota. For more information, see the about_Remote_Troubleshooting Help
topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : -2144108120,PSSessionOpenFailed
VERBOSE: Connecting to CAS2013.contoso.com.
New-PSSession : [cas2013.contoso.com] Connecting to remote server cas2013.contoso.com failed with the following error message :
The WS-Management service cannot process the request. The load quota for the system has been exceeded. Send future
requests at a slower rate or raise the system quota. For more information, see the about_Remote_Troubleshooting Help
topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : -2144108120,PSSessionOpenFailed
VERBOSE: Connecting to ca2-2013.contoso.com.
New-PSSession : [ca2-2013.contoso.com] Connecting to remote server ca2-2013.contoso.com failed with the following error message :
The WS-Management service cannot process the request. The load quota for the system has been exceeded. Send future
requests at a slower rate or raise the system quota. For more information, see the about_Remote_Troubleshooting Help
topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : -2144108120,PSSessionOpenFailed
VERBOSE: Connecting to MB2-2013.contoso.com.
VERBOSE: Connected to MB2-2013.contoso.com.
[PS] C:\Windows\system32>

Please try to restart WS-MAN on the server. This is being caused by default throttling policy.

Verify current setting and Try increasing PowerShellMaxConcurrency also make sure you always close any unwanted shell connections.

get-ThrottlingPolicy Default | fl PowerShellMaxConcurrency

Set-ThrottlingPolicy Default PowerShellMaxConcurrency <NumericValue>

Tried that and I'm still getting the issue.  There's two throttling policies, a default and a global policy, they were both set to 18.  So I could only change the default policy, and bumped that up to 1000.  The global policy is read-only and this cmdlet won't change that, even run as administrator.  Here's the output for my current throttling policy.

VERBOSE: Connected to MB2-2013.contoso.com.
[PS] C:\Windows\system32>get-ThrottlingPolicy | fl PowerShellMaxConcurrency

PowerShellMaxConcurrency : 1000

PowerShellMaxConcurrency : 18

[PS] C:\Windows\system32>get-ThrottlingPolicy

Name                                    ThrottlingPolicyScope                   IsServiceAccount
----                                    ---------------------                   ----------------
DefaultThrottlingPolicy_f79f53f7-088... Regular                                 False
GlobalThrottlingPolicy_8f04e8c7-a509... Global                                  False

Please have a look on below url

https://technet.microsoft.com/en-us/library/jj863577(v=exchg.150).aspx

Tried it. Still no dice.

This used to work until I deployed a second CAS. Would that have something to do with it?

Hi,

Is the cas2013.contoso.com the second CAS Server you added?

Whats the authentication settings on the powershell VD on the Back End Server. If the Anonymous is enabled, please disable it and restart the IIS to check if the issue persists.

Thanks,

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

Hi,

Is there any update on this thread?

Thanks,

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com